टाइपस्क्रिप्ट अतिरिक्त प्रॉपर्टी जाँच: आपकी ऑब्जेक्ट टाइप सुरक्षा को मजबूत करना

            
interface User {
  name: string;
  age: number;
}

const newUser: User = {
  name: 'Alice',
  age: 30,
  email: 'alice@example.com' // Error: Object literal may only specify known properties, and 'email' does not exist in type 'User'.
};

            

              
                Copy
              
            
          

            
interface Product {
  id: number;
  name: string;
}

function displayProduct(product: Product): void {
  console.log(`Product ID: ${product.id}, Name: ${product.name}`);
}

displayProduct({
  id: 101,
  name: 'Laptop',
  price: 1200 // Error: Argument of type '{ id: number; name: string; price: number; }' is not assignable to parameter of type 'Product'.
             // Object literal may only specify known properties, and 'price' does not exist in type 'Product'.
});

            

              
                Copy
              
            
          

            
interface Config {
  timeout: number;
}

function setupConfig(config: Config) {
  console.log(`Timeout set to: ${config.timeout}`);
}

const userProvidedConfig = {
  timeout: 5000,
  retries: 3 // This 'retries' property is an excess property according to 'Config'
};

setupConfig(userProvidedConfig); // No error!

// Even though userProvidedConfig has an extra property, the check is skipped
// because it's not an object literal being directly passed.
// TypeScript checks the type of userProvidedConfig itself.
// If userProvidedConfig was declared with type Config, an error would occur earlier.
// However, if declared as 'any' or a broader type, the error is deferred.

// A more precise way to show the bypass:
let anotherConfig;

if (Math.random() > 0.5) {
  anotherConfig = {
    timeout: 1000,
    host: 'localhost' // Excess property
  };
} else {
  anotherConfig = {
    timeout: 2000,
    port: 8080 // Excess property
  };
}

setupConfig(anotherConfig as Config); // No error due to type assertion and bypass

// The key is that 'anotherConfig' is not an object literal at the point of assignment to setupConfig.
// If we had an intermediate variable typed as 'Config', the initial assignment would fail.

// Example of intermediate variable:
let intermediateConfig: Config;

intermediateConfig = {
  timeout: 3000,
  logging: true // Error: Object literal may only specify known properties, and 'logging' does not exist in type 'Config'.
};

            

              
                Copy
              
            
          

            
interface Settings {
  theme: 'dark' | 'light';
}

const mySettings = {
  theme: 'dark',
  fontSize: 14 // Excess property
} as Settings;

// No error here because of the type assertion.
// We are telling TypeScript: "Trust me, this object conforms to Settings."
console.log(mySettings.theme);
// console.log(mySettings.fontSize); // This would cause a runtime error if fontSize wasn't actually there.

            

              
                Copy
              
            
          

            
interface FlexibleObject {
  id: number;
  [key: string]: any; // Allows any string key with any value
}

const flexibleItem: FlexibleObject = {
  id: 1,
  name: 'Widget',
  version: '1.0.0'
};

// No error because 'name' and 'version' are allowed by the index signature.
console.log(flexibleItem.name);

            

              
                Copy
              
            
          

            
interface BaseConfig {
  host: string;
}

interface ExtendedConfig extends BaseConfig {
  port: number;
}

const defaultConfig: BaseConfig = {
  host: 'localhost'
};

const userConfig = {
  port: 8080,
  timeout: 5000 // Excess property relative to BaseConfig, but expected by the merged type
};

// Spreading into a new object literal that conforms to ExtendedConfig
const finalConfig: ExtendedConfig = {
  ...defaultConfig,
  ...userConfig
};

// This is generally okay because 'finalConfig' is declared as 'ExtendedConfig'
// and the properties match. The check is on the type of 'finalConfig'.

// Let's consider a scenario where it *would* fail:

interface SmallConfig {
  key: string;
}

const data1 = { key: 'abc', value: 123 }; // 'value' is extra here
const data2 = { key: 'xyz', status: 'active' }; // 'status' is extra here

// Attempting to assign to a type that doesn't accommodate extras

// const combined: SmallConfig = {
//   ...data1, // Error: Object literal may only specify known properties, and 'value' does not exist in type 'SmallConfig'.
//   ...data2  // Error: Object literal may only specify known properties, and 'status' does not exist in type 'SmallConfig'.
// };

// The error occurs because the object literal formed by the spread syntax
// contains properties ('value', 'status') not present in 'SmallConfig'.

// If we create an intermediate variable with a broader type:

const temp: any = {
  ...data1,
  ...data2
};

// Then assign to SmallConfig, the excess property check is bypassed on the initial literal creation,
// but the type check on assignment might still occur if temp's type is inferred more strictly.
// However, if temp is 'any', no check happens until the assignment to 'combined'.

// Let's refine the understanding of spread with excess property checks:
// The check happens when the object literal created by the spread syntax is assigned
// to a variable or passed to a function that expects a more specific type.

interface SpecificShape { 
  id: number;
}

const objA = { id: 1, extra1: 'hello' };
const objB = { id: 2, extra2: 'world' };

// This will fail if SpecificShape doesn't allow 'extra1' or 'extra2':
// const merged: SpecificShape = {
//   ...objA,
//   ...objB
// };

// The reason it fails is that the spread syntax effectively creates a new object literal.
// If objA and objB had overlapping keys, the later one would win. The compiler
// sees this resulting literal and checks it against 'SpecificShape'.

// To make it work, you might need an intermediate step or a more permissive type:

const tempObj = {
  ...objA,
  ...objB
};

// Now, if tempObj has properties not in SpecificShape, the assignment will fail:
// const mergedCorrected: SpecificShape = tempObj; // Error: Object literal may only specify known properties...

// The key is that the compiler analyzes the shape of the object literal being formed.
// If that literal contains properties not defined in the target type, it's an error.

// The typical use case for spread syntax with excess property checks:

interface UserProfile {
  userId: string;
  username: string;
}

interface AdminProfile extends UserProfile {
  adminLevel: number;
}

const baseUserData: UserProfile = {
  userId: 'user-123',
  username: 'coder'
};

const adminData = {
  adminLevel: 5,
  lastLogin: '2023-10-27'
};

// This is where the excess property check is relevant:
// const adminProfile: AdminProfile = {
//   ...baseUserData,
//   ...adminData // Error: Object literal may only specify known properties, and 'lastLogin' does not exist in type 'AdminProfile'.
// };

// The object literal created by the spread has 'lastLogin', which isn't in 'AdminProfile'.
// To fix this, 'adminData' should ideally conform to AdminProfile or the excess property should be handled.

// Corrected approach:
const validAdminData = {
  adminLevel: 5
};

const adminProfileCorrect: AdminProfile = {
  ...baseUserData,
  ...validAdminData
};

console.log(adminProfileCorrect.userId);
console.log(adminProfileCorrect.adminLevel);

            

              
                Copy
              
            
          

            
interface UserProfile {
  id: number;
  name: string;
}

interface UserWithMetadata extends UserProfile {
  metadata: {
    [key: string]: any;
  };
}

// Or more commonly with a type alias and rest syntax:
type UserProfileWithMetadata = UserProfile & {
  [key: string]: any;
};

const user1: UserProfileWithMetadata = {
  id: 1,
  name: 'Bob',
  email: 'bob@example.com',
  isAdmin: true
};

// No error, as 'email' and 'isAdmin' are captured by the index signature in UserProfileWithMetadata.
console.log(user1.email);
console.log(user1.isAdmin);

// Another way using rest parameters in a type definition:
interface ConfigWithRest {
  apiUrl: string;
  timeout?: number;
  // Capture all other properties into 'extraConfig'
  [key: string]: any;
}

const appConfig: ConfigWithRest = {
  apiUrl: 'https://api.example.com',
  timeout: 5000,
  featureFlags: {
    newUI: true,
    betaFeatures: false
  }
};

console.log(appConfig.featureFlags);

            

              
                Copy
              
            
          

            
interface Employee {
  employeeId: string;
  department: string;
}

function processEmployeeData(data: Employee & { [key: string]: any }) {
  const { employeeId, department, ...otherDetails } = data;

  console.log(`Employee ID: ${employeeId}`);
  console.log(`Department: ${department}`);
  console.log('Other details:', otherDetails);
  // otherDetails will contain any properties not explicitly destructured,
  // like 'salary', 'startDate', etc.
}

const employeeInfo = {
  employeeId: 'emp-789',
  department: 'Engineering',
  salary: 90000,
  startDate: '2022-01-15'
};

processEmployeeData(employeeInfo);

// Even if employeeInfo had an extra property initially, the excess property check
// is bypassed if the function signature accepts it (e.g., using an index signature).
// If processEmployeeData was typed strictly as 'Employee', and employeeInfo had 'salary',
// an error would occur IF employeeInfo was an object literal passed directly.
// But here, employeeInfo is a variable, and the function's type handles extras.

            

              
                Copy
              
            
          

            
interface UserProfile {
  id: number;
  name: string;
  email?: string; // Optional email
}

const userWithEmail: UserProfile = {
  id: 2,
  name: 'Charlie',
  email: 'charlie@example.com'
};

const userWithoutEmail: UserProfile = {
  id: 3,
  name: 'David'
};

// If we try to add a property not in UserProfile:
// const userWithExtra: UserProfile = {
//   id: 4,
//   name: 'Eve',
//   phoneNumber: '555-1234'
// }; // Error: Object literal may only specify known properties, and 'phoneNumber' does not exist in type 'UserProfile'.

            

              
                Copy
              
            
          

            
interface ProductConfig {
  id: string;
  version: string;
}

// Imagine this comes from an external source or a less strict module
const externalConfig = {
  id: 'prod-abc',
  version: '1.2',
  debugMode: true // Excess property
};

// If you know 'externalConfig' will always have 'id' and 'version' and you want to treat it as ProductConfig:
const productConfig = externalConfig as ProductConfig;

// This assertion bypasses the excess property check on `externalConfig` itself.
// However, if you were to pass an object literal directly:

// const productConfigLiteral: ProductConfig = {
//   id: 'prod-xyz',
//   version: '2.0',
//   debugMode: false
// }; // Error: Object literal may only specify known properties, and 'debugMode' does not exist in type 'ProductConfig'.

            

              
                Copy
              
            
          

            
interface Shape {
  kind: 'circle' | 'square';
}

interface Circle extends Shape {
  kind: 'circle';
  radius: number;
}

interface Square extends Shape {
  kind: 'square';
  sideLength: number;
}

function calculateArea(shape: Shape) {
  if (shape.kind === 'circle') {
    // TypeScript knows 'shape' is a Circle here
    console.log(Math.PI * shape.radius ** 2);
  } else if (shape.kind === 'square') {
    // TypeScript knows 'shape' is a Square here
    console.log(shape.sideLength ** 2);
  }
}

const circleData = {
  kind: 'circle' as const, // Using 'as const' for literal type inference
  radius: 10,
  color: 'red' // Excess property
};

// When passed to calculateArea, the function signature expects 'Shape'.
// The function itself will correctly access 'kind'.
// If calculateArea were expecting 'Circle' directly and received circleData
// as an object literal, 'color' would be an issue.

// Let's illustrate the excess property check with a function expecting a specific subtype:

function processCircle(circle: Circle) {
  console.log(`Processing circle with radius: ${circle.radius}`);
}

// processCircle(circleData); // Error: Argument of type '{ kind: "circle"; radius: number; color: string; }' is not assignable to parameter of type 'Circle'.
                         // Object literal may only specify known properties, and 'color' does not exist in type 'Circle'.

// To fix this, you can destructure or use a more permissive type for circleData:

const { color, ...circleDataWithoutColor } = circleData;
processCircle(circleDataWithoutColor);

// Or define circleData to include a broader type:

const circleDataWithExtras: Circle & { [key: string]: any } = {
  kind: 'circle',
  radius: 15,
  color: 'blue'
};
processCircle(circleDataWithExtras); // Now it works.

            

              
                Copy